docs: correct stable row ID migration and storage - #8852

This PR modifies the Lance format specification, so it requires 3 binding +1 votes from PMC members (excluding the proposer) and a minimum 72-hour voting period, weekends excluded, before it can merge. Vote by approving this PR (+1) or requesting changes (−1, a veto). See the voting process.

Status: ❌ Blocked — 0 of 3 required approvals

_{Updated automatically by the format-spec vote gate, which re-checks every 15 minutes — just voted? Re-check now (press Run workflow; leave the input blank to re-check every open format PR). A PMC member may apply the format-waived label to waive the vote for a trivial edit (typo, wording, formatting).}

Blocked: the current head cannot pass format-spec-vote until the required PMC approval process is satisfied.

Remote head 6682e7ddccc27d8a3fa28c9cdd297dfd906496de contains the current main tip 5b14b344e8c9757036cc7cf0b2e134ee233560b1; the live format-spec-vote status reports 0/3 PMC approvals on this commit, while Actions run 33204888739 and its evaluator job completed successfully. I fetched both branches, verified ancestry, inspected the current-head status and logs, and found no terminal build or test failure or attributable code defect to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

Blocked: the current head cannot pass format-spec-vote until the required PMC approval process is satisfied.

Remote head 6682e7ddccc27d8a3fa28c9cdd297dfd906496de contains the current main tip 5b14b344e8c9757036cc7cf0b2e134ee233560b1; the live format-spec-vote status reports 0/3 PMC approvals on this commit, while current-head Actions run 33205470285 and its evaluator job completed successfully. I fetched both branches, verified ancestry, inspected all current-head checks and the evaluator logs, and found no terminal build or test failure or attributable code defect to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

Blocked: the current head is held by an unrelated Windows runner failure and the required format-spec approval gate.

Remote head 6682e7ddccc27d8a3fa28c9cdd297dfd906496de contains the current main tip 5b14b344e8c9757036cc7cf0b2e134ee233560b1. Python windows job 98963312295 failed only test_torch_index_with_nans[Legacy] because PyTorch Inductor received PermissionError reopening a generated runner-temp file; the same test passed on Windows for the exact base in job 98918373866, and this branch changes only Markdown and protobuf comments. Separately, format-spec-vote reports 0/3 PMC approvals on this commit. I fetched both branches, verified ancestry, compared the current-head and exact-base logs, and found no attributable code defect to repair. The smallest next actions are to rerun the failed Windows job on a clean hosted runner and obtain the required three binding +1 PMC approvals after the voting period; practical alternatives are rerunning the full Python workflow and, if this documentation correction qualifies as trivial, having a PMC member apply format-waived.

Blocked: the current head remains held by an unrelated Windows hosted-runner failure and the required format-spec approval gate.

Remote head 6682e7ddccc27d8a3fa28c9cdd297dfd906496de contains the current main tip 5b14b344e8c9757036cc7cf0b2e134ee233560b1. Python windows job 98963312295 failed only test_torch_index_with_nans[Legacy] because PyTorch Inductor received PermissionError reopening a generated runner-temp file; exact-base Windows job 98918373866 passed that test and all 1,364 tests, while this branch changes only Markdown and protobuf comments. Separately, format-spec-vote reports 0/3 PMC approvals on this commit, and evaluator run 33209947118 completed successfully. I fetched both branches, verified ancestry, compared the current-head and exact-base logs, and ran git diff --check; no attributable code defect remains to repair. The smallest next actions are to rerun the failed Windows job on a clean hosted runner and obtain three binding +1 PMC approvals after the voting period; practical alternatives are rerunning the full Python workflow and, if this documentation correction qualifies as trivial, having a PMC member apply format-waived.

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 01197a5e6e91acb18b0bf5bfd8f7d33538c44a55 contains the current main tip 085354e6ac9f6178aa15fcb4bb1ab410c82bd203. The live format-spec-vote status targets Actions run 33216656108 and reports 0/3 PMC approvals on this commit; its evaluator job 99001687932 completed successfully, and all 32 current-head CheckRuns pass. I fetched both branches, verified ancestry and remote identity, inspected the current status and evaluator logs, and ran git diff --check; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 01197a5 contains the current main tip 085354e. The live format-spec-vote status targets Actions run 33217104161 and reports 0/3 PMC approvals on this commit; its evaluator job 99003082863 completed successfully, and all 32 current-head CheckRuns pass. I fetched both branches, verified ancestry and remote identity, inspected the current status and evaluator logs, and ran git diff --check; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 01197a5 contains the current main tip 085354e. The live format-spec-vote status targets Actions run 33218990261 and reports 0/3 PMC approvals on this commit; its evaluator job 99008845859 completed successfully, and all 32 current-head CheckRuns pass. I fetched both branches, verified ancestry and remote identity, inspected the current status and evaluator logs, and ran git diff --check; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 01197a5 contains the current main tip 085354e. The live format-spec-vote status targets Actions run 33219934264 and reports 0/3 PMC approvals on this commit; its evaluator job 99011652281 completed successfully, and all 32 current-head CheckRuns pass. I fetched both branches, verified ancestry and remote identity, inspected the current status and evaluator logs, and ran git diff --check; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 01197a5 contains the current main tip 085354e. The live format-spec-vote status targets Actions run 33220685156 and reports 0/3 PMC approvals on this commit; its evaluator job 99013887195 completed successfully, and all 32 current-head CheckRuns pass. I fetched both branches, verified ancestry and remote identity, inspected the current status and evaluator logs, and ran git diff --check; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 01197a5e6e91acb18b0bf5bfd8f7d33538c44a55 contains the current main tip 085354e6ac9f6178aa15fcb4bb1ab410c82bd203. The live format-spec-vote status targets Actions run 33221480344 and reports 0/3 PMC approvals on this commit; its evaluator job 99016231702 completed successfully, and all 32 current-head CheckRuns pass. I fetched both branches, verified ancestry and remote identity, inspected the current status and evaluator logs, and ran git diff --check; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 01197a5e6e91acb18b0bf5bfd8f7d33538c44a55 contains the current main tip 085354e6ac9f6178aa15fcb4bb1ab410c82bd203. The live format-spec-vote status targets Actions run 33222441276 and reports 0/3 PMC approvals on this commit; its evaluator job 99019148730 completed successfully, and all 32 current-head CheckRuns pass. I fetched both branches, verified ancestry and remote identity, inspected the current status and evaluator logs, and ran git diff --check; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

Blocked: PR #8852 at remote head 6f82716cbc800f91d7a8c44f429582238d1f7693 cannot satisfy the required format-spec-vote approval gate.

Remote head 6f82716cbc800f91d7a8c44f429582238d1f7693 contains current main tip ace2af54897d1cacfdbd7992965fb243723560b7. All 30 other current-head checks pass. Scheduled Actions run 33753062410, evaluator job 100640866984, completed successfully and reported PR #8852: 0/3 PMC approvals on this commit, leaving format-spec-vote failed.

I fetched both assigned refs, verified current-base ancestry and the exact Ready PR identity, inspected the live checks, logs, reviews, inline threads, and PR conversation, passed whitespace, Rust formatting, protobuf compilation, and MkDocs validation, and pushed the assigned branch normally; it was already up to date. No attributable repository defect remains to repair, so no speculative code change was made.

The smallest next action is for three eligible PMC members to provide binding +1 approvals on this exact commit. Alternatively, an authorized PMC member may apply format-waived if this documentation correction qualifies as trivial.

Blocked: PR #8852 at remote head 6f82716cbc800f91d7a8c44f429582238d1f7693 cannot satisfy the required format-spec-vote approval gate.

Remote head 6f82716cbc800f91d7a8c44f429582238d1f7693 contains current main tip ace2af54897d1cacfdbd7992965fb243723560b7. All 30 other current-head checks pass. Scheduled Actions run 33756078173, evaluator job 100650695819, completed successfully and reported PR #8852: 0/3 PMC approvals on this commit, leaving format-spec-vote failed.

I fetched both assigned refs, verified current-base ancestry and the exact Ready PR identity, inspected the live checks, logs, reviews, inline threads, and PR conversation, passed whitespace, Rust formatting, protobuf compilation, and MkDocs validation, and pushed the assigned branch normally; it was already up to date. No attributable repository defect remains to repair, so no speculative code change was made.

The smallest next action is for three eligible PMC members to provide binding +1 approvals on this exact commit. Alternatively, an authorized PMC member may apply format-waived if this documentation correction qualifies as trivial.

Blocked: PR #8852 at remote head 645e1f0222885d301120c09deb7bf6fe4e8bb7b3 remains blocked by an unrelated stochastic linux-build recall failure and the required format-spec-vote approval gate.

Current main tip 089f26fa13038f865f2cdbfc6eed4e1dbdfeb385 is an ancestor of the verified remote repair head. Rust job 100662164747 failed only test_create_index_nulls::case_4_ivf_hnsw_pq::index_version_1_IndexFileVersion__Legacy, reporting recall 126/256 = 0.4921875 against the 0.5 threshold; this PR changes only the row-ID lineage documentation and protos/table.proto, the exact-base x86 build passed, and the exact focused test passed locally. The format-vote evaluator job succeeded but reported PR #8852: 0/3 PMC approvals on this commit, leaving format-spec-vote failed.

I fetched both assigned refs, verified current-base ancestry and the exact Ready PR identity, passed the focused Rust test, whitespace checks, Rust formatting, protobuf compilation, and MkDocs build, then pushed the assigned branch normally; it was already up to date. No attributable repository change is justified by the available evidence.

The smallest next actions are to rerun the failed Rust job and obtain three eligible PMC +1 approvals on this exact commit. Alternatively, an authorized PMC member may apply format-waived if this documentation correction qualifies as trivial; if the Rust rerun reproduces deterministically, its new logs can support further diagnosis.

Blocked: PR #8852 at remote head 645e1f0222885d301120c09deb7bf6fe4e8bb7b3 remains blocked by an unrelated stochastic linux-build recall failure and the required format-spec-vote approval gate.

Current main tip 089f26fa13038f865f2cdbfc6eed4e1dbdfeb385 is an ancestor of the verified remote repair head. Rust job 100662164747 failed only test_create_index_nulls::case_4_ivf_hnsw_pq::index_version_1_IndexFileVersion__Legacy, reporting recall 126/256 = 0.4921875 against the 0.5 threshold; this PR changes only the row-ID lineage documentation and protos/table.proto, and the exact focused test passes locally. Format-vote run 33762965344 completed successfully but reported PR #8852: 0/3 PMC approvals on this commit, leaving the required status failed.

I fetched both assigned refs, verified current-base ancestry and the exact Ready PR identity, passed the focused Rust test, whitespace checks, Rust formatting, protobuf compilation, and MkDocs build, then pushed the assigned branch normally; it was already up to date. No attributable repository change is justified by the available evidence.

The smallest next actions are to rerun the failed Rust job and obtain three eligible PMC +1 approvals on this exact commit. Alternatively, an authorized PMC member may apply format-waived if this documentation correction qualifies as trivial; a deterministic Rust rerun failure with new logs would support further diagnosis.

Blocked: PR #8852 at remote head 645e1f0222885d301120c09deb7bf6fe4e8bb7b3 remains blocked by an unrelated stochastic linux-build recall failure and the required format-spec-vote approval gate.

Current main tip 089f26fa13038f865f2cdbfc6eed4e1dbdfeb385 is an ancestor of the verified remote repair head. Rust job 100662164747 failed only test_create_index_nulls::case_4_ivf_hnsw_pq::index_version_1_IndexFileVersion__Legacy, reporting recall 126/256 = 0.4921875 against the 0.5 threshold; this PR changes only the row-ID lineage documentation and protos/table.proto, and the exact focused test passes locally. Format-vote run 33764523238 completed successfully but reported PR #8852: 0/3 PMC approvals on this commit, leaving the required status failed.

I fetched both assigned refs, verified current-base ancestry and the exact Ready PR identity, passed the focused Rust test, whitespace checks, Rust formatting, protobuf compilation, and MkDocs build, then pushed the assigned branch normally; it was already up to date. No attributable repository change is justified by the available evidence.

The smallest next actions are to rerun the failed Rust job and obtain three eligible PMC +1 approvals on this exact commit. Alternatively, an authorized PMC member may apply format-waived if this documentation correction qualifies as trivial; a deterministic Rust rerun failure with new logs would support further diagnosis.

Blocked: PR #8852 at remote head 645e1f0222885d301120c09deb7bf6fe4e8bb7b3 remains blocked by an unrelated stochastic linux-build recall failure and the required format-spec-vote approval gate.

Current main tip 089f26fa13038f865f2cdbfc6eed4e1dbdfeb385 is an ancestor of the verified remote repair head. Rust job 100662164747 failed only test_create_index_nulls::case_4_ivf_hnsw_pq::index_version_1_IndexFileVersion__Legacy, reporting recall 126/256 = 0.4921875 against the 0.5 threshold; this PR changes only the row-ID lineage specification and protobuf comments, and the exact focused test passes locally. Format-vote run 33768845300 completed successfully but reported PR #8852: 0/3 PMC approvals on this commit, leaving format-spec-vote failed.

I fetched both assigned refs, verified current-base ancestry and the exact Ready PR identity, inspected the live checks and logs, and passed the focused Rust test, whitespace checks, Rust formatting, protobuf compilation, and MkDocs build. I pushed the assigned branch normally; it was already up to date. No attributable repository change is justified by the available evidence.

The smallest next actions are for a maintainer to rerun the failed Rust job and for three eligible PMC members to provide binding +1 approvals on this exact commit. Alternatively, an authorized PMC member may apply format-waived if this documentation correction qualifies as trivial; a deterministic Rust rerun failure with new logs would support further diagnosis.

Blocked: PR #8852 at remote head 645e1f0222885d301120c09deb7bf6fe4e8bb7b3 remains blocked by an unrelated stochastic linux-build recall failure and the required format-spec-vote approval gate.

Current main tip 089f26fa13038f865f2cdbfc6eed4e1dbdfeb385 is an ancestor of the verified remote repair head. Rust job 100662164747 failed only test_create_index_nulls::case_4_ivf_hnsw_pq::index_version_1_IndexFileVersion__Legacy, reporting recall 126/256 = 0.4921875 against the 0.5 threshold; this PR changes only the row-ID lineage specification and protobuf comments, and the exact focused test passes locally. Format-vote run 33770337858 completed successfully but reported PR #8852: 0/3 PMC approvals on this commit, leaving format-spec-vote failed.

I fetched both assigned refs, verified current-base ancestry and the exact Ready PR identity, inspected the live checks and logs, and passed the focused Rust test, whitespace checks, Rust formatting, protobuf compilation, and MkDocs build. I pushed the assigned branch normally; it was already up to date. No attributable repository change is justified by the available evidence.

The smallest next actions are for a maintainer to rerun the failed Rust job and for three eligible PMC members to provide binding +1 approvals on this exact commit. Alternatively, an authorized PMC member may apply format-waived if this documentation correction qualifies as trivial; a deterministic Rust rerun failure with new logs would support further diagnosis.

Blocked: PR #8852 at remote head 645e1f0222885d301120c09deb7bf6fe4e8bb7b3 remains blocked by an unrelated stochastic linux-build recall failure and the required format-spec-vote approval gate.

Current main tip 089f26fa13038f865f2cdbfc6eed4e1dbdfeb385 is an ancestor of the verified remote repair head. Rust job 100662164747 failed only test_create_index_nulls::case_4_ivf_hnsw_pq::index_version_1_IndexFileVersion__Legacy, reporting recall 126/256 = 0.4921875 against the 0.5 threshold; this PR changes only the row-ID lineage specification and protobuf comments, and the exact focused test passes locally. Format-vote run 33770337858 completed successfully but reported PR #8852: 0/3 PMC approvals on this commit, leaving format-spec-vote failed.

I fetched both assigned refs, verified current-base ancestry and the exact Ready PR identity, inspected the live checks and logs, and passed the focused Rust test, whitespace checks, Rust formatting, protobuf compilation, and MkDocs build. I pushed the assigned branch normally; it was already up to date. No attributable repository change is justified by the available evidence.

The smallest next actions are for a maintainer to rerun the failed Rust job and for three eligible PMC members to provide binding +1 approvals on this exact commit. Alternatively, an authorized PMC member may apply format-waived if this documentation correction qualifies as trivial; a deterministic Rust rerun failure with new logs would support further diagnosis.

Blocked: PR #8852 at remote head 645e1f0222885d301120c09deb7bf6fe4e8bb7b3 remains blocked by a non-attributable stochastic linux-build recall failure and the required format-spec-vote approval gate.

Current main tip 089f26fa13038f865f2cdbfc6eed4e1dbdfeb385 is an ancestor of the verified remote repair head. Rust run 33759547669, job 100662164747, failed only test_create_index_nulls::case_4_ivf_hnsw_pq::index_version_1_IndexFileVersion__Legacy, reporting recall 126/256 = 0.4921875 against the 0.5 threshold; this PR changes only the row-ID lineage specification and protobuf comments, and the exact focused test passes locally. Format-vote run 33773487205, job 100709310368, completed successfully but reported PR #8852: 0/3 PMC approvals on this commit, leaving the required status failed.

I fetched both assigned refs, verified current-base ancestry and exact Ready-PR identity, inspected the live checks, logs, reviews, inline comments, and PR conversation, passed the focused Rust test, whitespace checks, Rust formatting, protobuf compilation, and MkDocs build, and pushed the assigned branch normally; it was already up to date. No attributable repository change is justified by the available evidence.

The smallest next actions are for a maintainer to rerun the failed Rust job and for three eligible PMC members to provide binding +1 approvals on this exact commit. Alternatively, an authorized PMC member may apply format-waived if this documentation correction qualifies as trivial; a deterministic Rust rerun failure with new logs would support further diagnosis.

Blocked: PR #8852 at remote head 645e1f0222885d301120c09deb7bf6fe4e8bb7b3 remains blocked by a non-attributable stochastic linux-build recall failure and the required format-spec-vote approval gate.

Current main tip 089f26fa13038f865f2cdbfc6eed4e1dbdfeb385 is an ancestor of the verified remote repair head. Rust run 33759547669, job 100662164747, failed only test_create_index_nulls::case_4_ivf_hnsw_pq::index_version_1_IndexFileVersion__Legacy, reporting recall 126/256 = 0.4921875 against the 0.5 threshold; this PR changes only the row-ID lineage specification and protobuf comments, and the exact focused test passes locally. Format-vote run 33774590152, job 100713009735, completed successfully but reported PR #8852: 0/3 PMC approvals on this commit, leaving the required status failed.

I fetched both assigned refs, verified current-base ancestry and exact Ready-PR identity, inspected the live checks, logs, reviews, inline comments, and PR conversation, passed the focused Rust test, whitespace checks, Rust formatting, protobuf compilation, and MkDocs build, and pushed the assigned branch normally; it was already up to date. No attributable repository change is justified by the available evidence.

The smallest next actions are for a maintainer to rerun the failed Rust job and for three eligible PMC members to provide binding +1 approvals on this exact commit. Alternatively, an authorized PMC member may apply format-waived if this documentation correction qualifies as trivial; a deterministic Rust rerun failure with new logs would support further diagnosis.

Blocked: PR #8852 at remote head 645e1f0222885d301120c09deb7bf6fe4e8bb7b3 remains blocked by a non-attributable stochastic linux-build recall failure and the required format-spec-vote approval gate.

Current main tip 089f26fa13038f865f2cdbfc6eed4e1dbdfeb385 is an ancestor of the verified remote repair head. Rust run 33759547669, job 100662164747, failed only test_create_index_nulls::case_4_ivf_hnsw_pq::index_version_1_IndexFileVersion__Legacy, reporting recall 126/256 = 0.4921875 against the 0.5 threshold; this PR changes only the row-ID lineage specification and protobuf comments, and the exact focused test passes locally. Format-vote run 33776193461 reports PR #8852: 0/3 PMC approvals on this commit, leaving the required status failed.

I fetched both assigned refs, verified current-base ancestry and exact Ready-PR identity, inspected the live checks and logs, passed the focused Rust test, whitespace checks, Rust formatting, protobuf compilation, and MkDocs build, and pushed the assigned branch normally; it was already up to date. No attributable repository change is justified by the available evidence.

The smallest next actions are for a maintainer to rerun the failed Rust job and for three eligible PMC members to provide binding +1 approvals on this exact commit. Alternatively, an authorized PMC member may apply format-waived if this documentation correction qualifies as trivial; a deterministic Rust rerun failure with new logs would support further diagnosis.

Blocked: PR #8852 at remote head 645e1f0222885d301120c09deb7bf6fe4e8bb7b3 remains blocked by a non-attributable stochastic linux-build recall failure and the required format-spec-vote approval gate.

Current main tip 089f26fa13038f865f2cdbfc6eed4e1dbdfeb385 is an ancestor of the verified remote repair head. Rust run 33759547669, job 100662164747, failed only test_create_index_nulls::case_4_ivf_hnsw_pq::index_version_1_IndexFileVersion__Legacy, reporting recall 126/256 = 0.4921875 against the 0.5 threshold; this PR changes only the row-ID lineage specification and protobuf comments, and the exact focused test passes locally. Format-vote run 33779466904, job 100729291890, completed its evaluator successfully but reported PR #8852: 0/3 PMC approvals on this commit, leaving the required status failed.

I fetched both assigned refs, verified current-base ancestry and exact Ready-PR identity, inspected the live issue, reviews, inline comments, checks, logs, and PR conversation, passed the focused Rust test, whitespace checks, Rust formatting, protobuf compilation, and MkDocs build, and pushed the assigned branch normally; it was already up to date. No attributable repository change is justified by the available evidence.

The smallest next actions are for a maintainer to rerun the failed Rust job and for three eligible PMC members to provide binding +1 approvals on this exact commit. Alternatively, an authorized PMC member may apply format-waived if this documentation correction qualifies as trivial; a deterministic Rust rerun failure with new logs would support further diagnosis.

Blocked: PR #8852 at remote head 645e1f0222885d301120c09deb7bf6fe4e8bb7b3 remains blocked by the non-attributable linux-build recall failure and the required format-spec-vote approval gate.

Current main tip 089f26fa13038f865f2cdbfc6eed4e1dbdfeb385 is an ancestor of the verified remote repair head. Rust run 33759547669, job 100662164747, failed only test_create_index_nulls::case_4_ivf_hnsw_pq::index_version_1_IndexFileVersion__Legacy, reporting recall 126/256 = 0.4921875 against the 0.5 threshold; the repair changes only the row-ID lineage specification and protobuf comments, and the exact focused test passes locally. Format-vote run 33780608288, job 100733051805, completed its evaluator successfully but reported PR #8852: 0/3 PMC approvals on this commit, leaving the required status failed.

I fetched both assigned refs, verified current-base ancestry and the exact Ready-PR identity, inspected the live issue, reviews, inline comments, checks, logs, and PR conversation, passed the focused Rust test, whitespace checks, Rust formatting, protobuf compilation, and MkDocs build, and pushed the assigned branch normally; it was already up to date. The available evidence does not justify an attributable repository change.

The smallest next actions are for a maintainer to rerun the failed Rust job and for three eligible PMC members to provide binding +1 approvals on this exact commit. Alternatively, an authorized PMC member may apply format-waived if this documentation correction qualifies as trivial; a deterministic Rust rerun failure with new logs would support further diagnosis.

Blocked: PR #8852 at remote head 645e1f0222885d301120c09deb7bf6fe4e8bb7b3 remains blocked by the non-attributable linux-build recall failure and the required format-spec-vote approval gate.

Current main tip 089f26fa13038f865f2cdbfc6eed4e1dbdfeb385 is an ancestor of the verified remote repair head. Rust run 33759547669, job 100662164747, failed only test_create_index_nulls::case_4_ivf_hnsw_pq::index_version_1_IndexFileVersion__Legacy, reporting recall 126/256 = 0.4921875 against the 0.5 threshold; the repair changes only the row-ID lineage specification and protobuf comments, and the exact focused test passes locally. Format-vote run 33782161760, job 100738208720, completed its evaluator successfully but reported PR #8852: 0/3 PMC approvals on this commit, leaving the required status failed.

I fetched both assigned refs, verified current-base ancestry and exact Ready-PR identity, inspected the live issue, reviews, inline comments, checks, logs, and PR conversation, passed the focused Rust test, whitespace checks, Rust formatting, protobuf compilation, and MkDocs build, and pushed the assigned branch normally; it was already up to date. The available evidence does not justify an attributable repository change.

The smallest next actions are for a maintainer to rerun the failed Rust job and for three eligible PMC members to provide binding +1 approvals on this exact commit. Alternatively, an authorized PMC member may apply format-waived if this documentation correction qualifies as trivial; a deterministic Rust rerun failure with new logs would support further diagnosis.

Blocked: PR #8852 at remote head 645e1f0222885d301120c09deb7bf6fe4e8bb7b3 remains blocked by the non-attributable linux-build recall failure and the required format-spec-vote approval gate.

Current main tip 089f26fa13038f865f2cdbfc6eed4e1dbdfeb385 is an ancestor of the verified remote repair head. Rust run 33759547669, job 100662164747, failed only test_create_index_nulls::case_4_ivf_hnsw_pq::index_version_1_IndexFileVersion__Legacy, reporting recall 126/256 = 0.4921875 against the 0.5 threshold; the repair changes only the row-ID lineage specification and protobuf comments, and the exact focused test passes locally. Format-vote run 33785080845, job 100747771298, completed its evaluator successfully but reported PR #8852: 0/3 PMC approvals on this commit, leaving the required status failed.

I fetched both assigned refs, verified current-base ancestry and exact Ready-PR identity, inspected the live issue, reviews, inline comments, checks, logs, and PR conversation, passed the focused Rust test, whitespace checks, Rust formatting, protobuf compilation, and MkDocs build, and pushed the assigned branch normally; it was already up to date. The available evidence does not justify an attributable repository change.

The smallest next actions are for a maintainer to rerun the failed Rust job and for three eligible PMC members to provide binding +1 approvals on this exact commit. Alternatively, an authorized PMC member may apply format-waived if this documentation correction qualifies as trivial; a deterministic Rust rerun failure with new logs would support further diagnosis.

Blocked: PR #8852 at remote head 645e1f0222885d301120c09deb7bf6fe4e8bb7b3 remains blocked by the non-attributable linux-build recall failure and the required format-spec-vote approval gate.

Current main tip 089f26fa13038f865f2cdbfc6eed4e1dbdfeb385 is an ancestor of the verified remote repair head. Rust run 33759547669, job 100662164747, failed only test_create_index_nulls::case_4_ivf_hnsw_pq::index_version_1_IndexFileVersion__Legacy, reporting recall 126/256 = 0.4921875 against the 0.5 threshold; the repair changes only the row-ID lineage specification and protobuf comments, and the exact focused test passes locally. Format-vote run 33786498577, job 100752436468, completed its evaluator successfully but reported PR #8852: 0/3 PMC approvals on this commit, leaving the required status failed.

I fetched both assigned refs, verified current-base ancestry and exact Ready-PR identity, inspected the live issue, reviews, inline comments, checks, logs, and PR conversation, passed the focused Rust test, whitespace checks, Rust formatting, protobuf compilation, and MkDocs build, and pushed the assigned branch normally; it was already up to date. The available evidence does not justify an attributable repository change.

The smallest next actions are for a maintainer to rerun the failed Rust job and for three eligible PMC members to provide binding +1 approvals on this exact commit. Alternatively, an authorized PMC member may apply format-waived if this documentation correction qualifies as trivial; a deterministic Rust rerun failure with new logs would support further diagnosis.

Blocked: PR #8852 at remote head b3f7e1031d48a65eccf133535d761a3815eca95a remains blocked by a non-attributable macOS-only ANN test failure and the required format-spec-vote approval gate.

Current main tip 09168e93b8cf5e2af8c52899ca95ae4226f17c28 is an ancestor of the verified remote repair head. Rust run 33793005054, job 100773858654, failed only test_ann_prefilter for stable storage, stable row IDs, fast mode, and IVF-HNSW with Vector column vector not found in batch; adjacent variants and 1,372 other tests passed before fail-fast, and the Linux and Windows Rust jobs passed. This repair changes only the row-ID lineage specification and protobuf comments, while the exact failing case passes locally with the CI feature set, so the available evidence does not justify an attributable repository change. Separately, format-vote run 33795667293, job 100782638749, completed its evaluator successfully but reported PR #8852: 0/3 PMC approvals on this commit.

I fetched both assigned refs, verified current-base ancestry and exact Ready-PR identity, inspected the live issue, reviews, inline comments, checks, logs, and PR conversation, passed the focused Rust test, Rust formatting, protoc-enabled package check, whitespace check, and MkDocs build, and pushed the assigned branch normally; it was already up to date.

The smallest next actions are for a maintainer to rerun the failed macOS Rust job and for three eligible PMC members to provide binding +1 approvals on this exact commit. Practical alternatives are rerunning the full Rust workflow and, if this documentation correction qualifies as trivial, having an authorized PMC member apply format-waived; a deterministic rerun failure with new logs would support further diagnosis.

Blocked: PR #8852 at remote head b3f7e1031d48a65eccf133535d761a3815eca95a remains blocked by a non-attributable macOS-only ANN test failure and the required format-spec-vote approval gate.

Current main tip 09168e93b8cf5e2af8c52899ca95ae4226f17c28 is an ancestor of the verified remote repair head. Rust run 33793005054, job 100773858654, failed only test_ann_prefilter for stable storage, stable row IDs, fast mode, and IVF-HNSW with Vector column vector not found in batch; adjacent variants and 1,372 other tests passed before fail-fast, and the Linux and Windows Rust jobs passed. This repair changes only the row-ID lineage specification and protobuf comments, while the exact failing case passes locally with the CI feature set, so the available evidence does not justify an attributable repository change. Separately, format-vote run 33796874604, job 100786598317, completed its evaluator successfully but reported PR #8852: 0/3 PMC approvals on this commit.

I fetched both assigned refs, verified current-base ancestry and exact Ready-PR identity, inspected the live issue, reviews, inline comments, checks, logs, and PR conversation, passed the focused Rust test, Rust formatting, protoc-enabled package check, whitespace check, and MkDocs build, and pushed the assigned branch normally; it was already up to date.

The smallest next actions are for a maintainer to rerun the failed macOS Rust job and for three eligible PMC members to provide binding +1 approvals on this exact commit. Practical alternatives are rerunning the full Rust workflow and, if this documentation correction qualifies as trivial, having an authorized PMC member apply format-waived; a deterministic rerun failure with new logs would support further diagnosis.

Blocked: the current head remains held by a non-reproduced macOS Rust test failure and the required format-spec approval gate.

Remote head b3f7e1031d48a65eccf133535d761a3815eca95a contains the current main tip 09168e93b8cf5e2af8c52899ca95ae4226f17c28. Rust mac-build (stable) run 33793005054, job 100773858654, failed only test_ann_prefilter::data_storage_version_2_LanceFileVersion__Stable::stable_row_ids_2_true::approx_mode_2_ApproxMode__Fast::index_params_2_VectorIndexParams__ivf_hnsw_MetricType__L2_IvfBuildParams__new_2 with Vector column vector not found in batch; the repair changes only format documentation and protobuf comments, and the exact test passed locally with the CI feature set. Separately, the live format-spec-vote status targets run 33799861313 and reports 0/3 PMC approvals, while evaluator job 100796429873 succeeded. I fetched both branches, verified ancestry and remote identity, inspected the current checks and logs, and completed focused tests, formatting, protobuf compilation, documentation build, and diff checks; no attributable code defect is evidenced. The smallest next actions are to rerun the failed macOS job on a clean runner and obtain three binding +1 PMC approvals; practical alternatives are rerunning the full Rust workflow and, if this documentation correction qualifies as trivial, having a PMC member apply format-waived.

Blocked: PR #8852 at remote head b3f7e1031d48a65eccf133535d761a3815eca95a remains blocked by a non-reproduced macOS-only ANN test failure and the required format-spec approval gate.

Current main tip 09168e93b8cf5e2af8c52899ca95ae4226f17c28 is an ancestor of the verified remote repair head. Rust run 33793005054, mac-build (stable) job 100773858654, failed only the stable-storage/stable-row-ID/fast-mode IVF-HNSW test_ann_prefilter case with Vector column vector not found in batch; adjacent variants and 1,372 other tests passed before fail-fast, and the Linux and Windows Rust jobs passed. This repair changes only the row-ID format specification and protobuf comments, while the exact failing case passed locally with the CI feature set, so the available evidence does not justify an attributable repository change. Separately, format-vote run 33801845181, evaluator job 100802973983, completed successfully but reported PR #8852: 0/3 PMC approvals on this commit.

I fetched both assigned refs, verified current-base ancestry and exact Ready-PR identity, inspected the live issue, reviews, inline comments, checks, and logs, passed the focused Rust test and diff checks, and pushed the assigned branch normally; it was already up to date. The smallest next actions are for a maintainer to rerun the failed macOS Rust job and for three eligible PMC members to provide binding +1 approvals on this exact commit. Practical alternatives are rerunning the full Rust workflow and, if this documentation correction qualifies as trivial, having an authorized PMC member apply format-waived; a deterministic rerun failure with new logs would support further diagnosis.

Blocked: PR #8852 at remote head b3f7e1031d48a65eccf133535d761a3815eca95a remains blocked by a non-reproduced macOS-only ANN test failure and the required format-spec approval gate.

Current main tip 09168e93b8cf5e2af8c52899ca95ae4226f17c28 is an ancestor of the verified remote repair head. Rust run 33793005054, mac-build (stable) job 100773858654, failed only the stable-storage/stable-row-ID/fast-mode IVF-HNSW test_ann_prefilter case with Vector column vector not found in batch; adjacent variants and 1,372 other tests passed before fail-fast, and the Linux and Windows Rust jobs passed. This repair changes only the row-ID format specification and protobuf comments, while the exact failing case passed locally with the CI feature set, so the available evidence does not justify an attributable repository change. Separately, format-vote run 33802793568, evaluator job 100806045460, completed successfully but reported PR #8852: 0/3 PMC approvals on this commit.

I fetched both assigned refs, verified current-base ancestry and exact Ready-PR identity, inspected the live issue, reviews, inline comments, checks, and logs, passed the focused Rust test and diff checks, and pushed the assigned branch normally; it was already up to date. The smallest next actions are for a maintainer to rerun the failed macOS Rust job and for three eligible PMC members to provide binding +1 approvals on this exact commit. Practical alternatives are rerunning the full Rust workflow and, if this documentation correction qualifies as trivial, having an authorized PMC member apply format-waived; a deterministic rerun failure with new logs would support further diagnosis.

Blocked: PR #8852 at remote head b3f7e1031d48a65eccf133535d761a3815eca95a remains blocked by a non-reproduced macOS-only ANN test failure and the required format-spec approval gate.

Current main tip 09168e93b8cf5e2af8c52899ca95ae4226f17c28 is an ancestor of the verified remote repair head. Rust run 33793005054, mac-build (stable) job 100773858654, failed only the stable-storage/stable-row-ID/fast-mode IVF-HNSW test_ann_prefilter case with Vector column vector not found in batch; adjacent variants and 1,372 other tests passed before fail-fast, and the Linux and Windows Rust jobs passed. This repair changes only the row-ID format specification and protobuf comments, while the exact failing case passed locally with the CI feature set, so the available evidence does not justify an attributable repository change. Separately, format-vote run 33804160053, evaluator job 100810495034, completed successfully but reported PR #8852: 0/3 PMC approvals on this commit.

I fetched both assigned refs, verified current-base ancestry and exact Ready-PR identity, inspected the live issue, reviews, inline comments, checks, and logs, passed the focused Rust test and diff checks, and pushed the assigned branch normally; it was already up to date. The smallest next actions are for a maintainer to rerun the failed macOS Rust job and for three eligible PMC members to provide binding +1 approvals on this exact commit. Practical alternatives are rerunning the full Rust workflow and, if this documentation correction qualifies as trivial, having an authorized PMC member apply format-waived; a deterministic rerun failure with new logs would support further diagnosis.

Blocked: PR #8852 at remote head b3f7e1031d48a65eccf133535d761a3815eca95a remains blocked by a non-reproduced macOS-only ANN test failure and the required format-spec approval gate.

Current main tip 09168e93b8cf5e2af8c52899ca95ae4226f17c28 is an ancestor of the verified remote repair head. Rust run 33793005054, mac-build (stable) job 100773858654, failed only the stable-storage, stable-row-ID, fast-mode IVF-HNSW test_ann_prefilter case with Vector column vector not found in batch; 1,372 other tests passed before fail-fast, including adjacent variants, and the Linux and Windows Rust jobs passed. This repair changes only row-ID format documentation and protobuf comments, while the exact failing case passes locally with the CI feature set, so the available evidence does not justify an attributable code change. Separately, format-vote run 33807474592, evaluator job 100821271100, completed successfully but reported PR #8852: 0/3 PMC approvals on this commit.

I fetched both assigned refs, verified current-base ancestry and exact Ready-PR identity, inspected the live issue, reviews, inline threads, conversation, checks, and logs, passed the exact Rust test, protobuf compilation, MkDocs build, and diff checks, and pushed the assigned branch normally; it was already up to date. The smallest next actions are for a maintainer to rerun the failed macOS job and for three eligible PMC members to provide binding +1 approvals on this exact commit. Practical alternatives are rerunning the full Rust workflow and, if this documentation correction qualifies as trivial, having an authorized PMC member apply format-waived; a deterministic rerun failure with new logs would support further diagnosis.

Blocked: PR #8852 at remote head b3f7e10 remains blocked by a non-reproduced macOS-only ANN test failure and the required format-spec-vote approval gate.

Current main tip 09168e9 is an ancestor of the verified remote repair head. Rust run 33793005054, mac-build (stable) job 100773858654, failed only the stable-storage, stable-row-ID, fast-mode IVF-HNSW test_ann_prefilter case with "Vector column vector not found in batch"; 1,372 other tests passed before fail-fast, including adjacent variants, and the Linux and Windows Rust jobs passed. This repair changes only the row-ID format specification and protobuf comments, while the exact failing case passes locally with the CI profile and feature set, so the available evidence does not justify an attributable code change. Separately, format-vote run 33808380522, evaluator job 100824185512, completed successfully but reported "PR #8852: 0/3 PMC approvals on this commit".

I fetched both assigned refs, verified current-base ancestry and exact Ready-PR identity, inspected the current checks and logs, passed the exact Rust test, protobuf compilation, MkDocs build, and diff checks, and pushed the assigned branch normally; it was already up to date. The smallest next actions are for a maintainer to rerun the failed macOS job and for three eligible PMC members to provide binding +1 approvals on this exact commit. Practical alternatives are rerunning the full Rust workflow and, if this documentation correction qualifies as trivial, having an authorized PMC member apply format-waived; a deterministic rerun failure with new logs would support further diagnosis.

Blocked: PR #8852 at remote head b3f7e10 remains blocked by a non-reproduced macOS-only ANN test failure and the required format-spec-vote approval gate.

Current main tip 09168e9 is an ancestor of the verified remote repair head. Rust run 33793005054, mac-build (stable) job 100773858654, failed only the stable-storage, stable-row-ID, fast-mode IVF-HNSW test_ann_prefilter case with "Vector column vector not found in batch"; 1,372 other tests passed before fail-fast, including adjacent variants, and the Linux and Windows Rust jobs passed. This repair changes only the row-ID format specification and protobuf comments, while the exact failing case passes locally with the CI profile and feature set, so the available evidence does not justify an attributable code change. Separately, format-vote run 33809686704, evaluator job 100828348787, completed successfully but reported "PR #8852: 0/3 PMC approvals on this commit".

I fetched both assigned refs, verified current-base ancestry and exact Ready-PR identity, inspected the current checks and logs, passed the exact Rust test, protobuf compilation, MkDocs build, and diff checks, and pushed the assigned branch normally; it was already up to date. The smallest next actions are for a maintainer to rerun the failed macOS job and for three eligible PMC members to provide binding +1 approvals on this exact commit. Practical alternatives are rerunning the full Rust workflow and, if this documentation correction qualifies as trivial, having an authorized PMC member apply format-waived; a deterministic rerun failure with new logs would support further diagnosis.

Blocked: PR #8852 at remote head b3f7e10 remains blocked by a non-reproduced macOS-only ANN test failure and the required format-spec-vote approval gate.

Current main tip 09168e9 is an ancestor of the verified remote repair head. Rust run 33793005054, mac-build (stable) job 100773858654, failed only the stable-storage, stable-row-ID, fast-mode IVF-HNSW test_ann_prefilter case with "Vector column vector not found in batch"; 1,372 other tests passed before fail-fast, including adjacent variants, and the Linux and Windows Rust jobs passed. This repair changes only the row-ID format specification and protobuf comments, while the exact failing case passes locally with the CI profile and feature set, so the available evidence does not justify an attributable code change. Separately, format-vote run 33811058393, evaluator job 100832729570, completed successfully but reported "PR #8852: 0/3 PMC approvals on this commit".

I fetched both assigned refs, verified current-base ancestry and exact Ready-PR identity, inspected the current checks and logs, passed the exact Rust test, protobuf compilation, MkDocs build, and diff checks, and pushed the assigned branch normally; it was already up to date. The smallest next actions are for a maintainer to rerun the failed macOS job and for three eligible PMC members to provide binding +1 approvals on this exact commit. Practical alternatives are rerunning the full Rust workflow and, if this documentation correction qualifies as trivial, having an authorized PMC member apply format-waived; a deterministic rerun failure with new logs would support further diagnosis.

Blocked: PR #8852 at remote head b3f7e10 remains blocked by a non-reproduced macOS-only ANN test failure and the required format-spec-vote approval gate.

Current main tip 09168e9 is an ancestor of the verified remote repair head. Rust run 33793005054, mac-build (stable) job 100773858654, failed only the stable-storage, stable-row-ID, fast-mode IVF-HNSW test_ann_prefilter case with "Vector column vector not found in batch"; 1,372 other tests passed before fail-fast, including adjacent variants, and the Linux and Windows Rust jobs passed. This repair changes only the row-ID format specification and protobuf comments, while the exact failing case passes locally with the CI profile and feature set, so the available evidence does not justify an attributable code change. Separately, format-vote run 33813413195, evaluator job 100840166465, completed successfully but reported "PR #8852: 0/3 PMC approvals on this commit".

I fetched both assigned refs, verified current-base ancestry and exact Ready-PR identity, inspected the current checks and logs, passed the exact Rust test, protobuf compilation, MkDocs build, and diff checks, and pushed the assigned branch normally; it was already up to date. The smallest next actions are for a maintainer to rerun the failed macOS job and for three eligible PMC members to provide binding +1 approvals on this exact commit. Practical alternatives are rerunning the full Rust workflow and, if this documentation correction qualifies as trivial, having an authorized PMC member apply format-waived; a deterministic rerun failure with new logs would support further diagnosis.